-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding reencryption command to DKG #251
Conversation
Pull Request Test Coverage Report for Build 5597440153
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First batch of review :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Meta-comment:
I'm wondering, does it make sense to add Calypso-specific stuff to our Pedersen's implementation, or should we do a Calypso-specific DKG (in its own repo) using this implementation and extending it ? 🤔
I'm just a bit worried of overspecializing our Pedersen implementation while at the same time slowing down our development (because I'll tend to be slightly more annoying on the Dela repo, since it's the foundation for everything else)
dkg/pedersen/pedersen.go
Outdated
} | ||
|
||
// DecryptSecret implements dkg.Actor. | ||
func (a *Actor) DecryptSecret(Cs []kyber.Point, XhatEnc kyber.Point, Sk kyber.Scalar) (msg []byte, err error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we misunderstood each other 😅
I didn't mean the OCS (although it's probably a good thing that you have split it out).
I meant the secret decryption seems off here (as we discussed in person yesterday), and it probably makes more sense into its own (client) library.
Kudos, SonarCloud Quality Gate passed! |
No description provided.